Limit creation of new issues and clarify bug report process #9690
Conversation
|
First off, thanks for all the great work that has gone into DRF! ❤️ Just wanted to add a viewpoint as user of DRF. It was shocking/worrying when the issues and discussions were hidden wholesale earlier (see some comments here: https://github.com/orgs/encode/discussions/11). It signaled to me not this project wasn't just "done" (the intention) but felt more like "dead". I worried that if new users came to DRF and saw that state, they would be turned away and thus the project would slowly lose relevance and activity. I'm glad to see that this has been reverted. I wanted to share my recommendation that whatever state this lands on, that it still allows users to easily report/discuss issues as it has a big impact on how the project is perceived. |
| blank_issues_enabled: false | ||
| contact_links: | ||
| - name: Bug report | ||
| url: https://github.com/encode/django-rest-framework/compare |
There was a problem hiding this comment.
Missed a trailing slash here..
|
Going to close that as we have issues and discussions again. IMO, we should instead restore and review the content that was removed in #9660. My personal stance is that we should make it difficult to open issues, and push people to start with a discussion instead. If the issue is valid and worth a fix, then maintainers can always convert the discussion to an issue, if needed. |
Description
As follow up from #9660, limit new issue creation and clarify process for reporting bugs.
This is how it looks: